-
Notifications
You must be signed in to change notification settings - Fork 16
Update Level 1b consumable availability to reflect 1b-2 merge #1743
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…d average of availability at levels 1b and 2
|
Availability at level 1b is updated with average of availability (by item_code and month) for levels 1b and 2. Three strategies of weighting are adopted to test calibration -
New RF :
New RF :
New RF :
|
|
Hi @tbhallett. As discussed earlier this week, I've added three new versions of the consumable availability RF on this branch to see how each of these performs in comparison with data.
|
|
now running on Azure: |
|
Errors with the workflow have been resolved - this PR's calibration workflow is now running! |
|
@sakshimohan -- I've looked at the calibration runs for this, and nothing disastrous has happened -- so I think it's OK to proceed. |
Many thanks, @tbhallett! I assume any of the four weighting options are OK? In this case, I'll use |
Ok, that's fine to proceed then. I also made this graph to help (me) remember the difference between that scenario and what's in master:
|
This is really helpful. Just to note the reason that the availability is so vastly different for Salima, Ntchisi, Mwanza, Machinga, and Balaka (Facility IDs 2, 54, 70 102, 114) is that no facilities at level 1b were recorded in these districts as per HHFA. This means that the availability at level 1b is equated to that at level 2. |
I see. I'd leave it to your best judgement on that then. |

This PR updates the RF for consumable availability for level 1b facilities to reflect the merging of level 1b and 2 in simulations.